SUPPORT / SAMPLES & SAS NOTES
Problem Note 61624: When you re-run flows that use temporary or partitioned data, have an out-of-date state, or are always-run tasks, the run might fail
 |  |  |  |  |
In SAS® Infrastructure for Risk Management, if you attempt to re-run a flow instance that uses temporary or partitioned data, has an out-of-date state, or is an always-run task, the run might fail. When this issue occurs, an error similar to the following is generated in the logs:
ERROR: Could not move and link one or more files to '/install/RiskTesting/SASConfig/Lev1/AppData/SASIRM/pa/pool/_649'
An error(s) occurred executing file action "SymbolicLink.moveAndLink" it had 1 errors in the execution log.
java.io.IOException: An error(s) occurred executing file action "SymbolicLink.moveAndLink" it had 1 errors in the execution log.
at com.sas.solutions.risk.irm.server.io.WorkspaceServerWorker.executeSASCode(WorkspaceServerWorker.java:571)
at com.sas.solutions.risk.irm.server.io.IOUtils.executeIOSASCodeWithRetry(IOUtils.java:934)
at com.sas.solutions.risk.irm.server.io.IOUtils.executeRemoteCodeAndCaptureException(IOUtils.java:738)
at com.sas.solutions.risk.irm.server.io.SymbolicLink.moveAndLink(SymbolicLink.java:936)
at com.sas.solutions.risk.irm.server.pooling.DataObjectPoolingService.moveAndLink(DataObjectPoolingService.java:376)
at com.sas.solutions.risk.irm.server.pooling.DataObjectPoolingService.poolOutputs(DataObjectPoolingService.java:400)
at com.sas.solutions.risk.irm.server.pooling.DataObjectPoolingService.access$000(DataObjectPoolingService.java:66)
at com.sas.solutions.risk.irm.server.pooling.DataObjectPoolingService$1.update(DataObjectPoolingService.java:341)
at java.util.Observable.notifyObservers(Observable.java:159)
at java.util.Observable.notifyObservers(Observable.java:115)
[...]
at com.sas.solutions.risk.irm.server.io.WorkspaceServerWorker.executeSASCode(WorkspaceServerWorker.java:571)
at com.sas.solutions.risk.irm.server.io.IOUtils.executeIOSASCodeWithRetry(IOUtils.java:934)
at com.sas.solutions.risk.irm.server.io.IOUtils.executeRemoteCodeAndCaptureException(IOUtils.java:738)
at com.sas.solutions.risk.irm.server.io.SymbolicLink.moveAndLink(SymbolicLink.java:936)
at com.sas.solutions.risk.irm.server.pooling.DataObjectPoolingService.moveAndLink(DataObjectPoolingService.java:376)
at com.sas.solutions.risk.irm.server.pooling.DataObjectPoolingService.poolOutputs(DataObjectPoolingService.java:400)
at com.sas.solutions.risk.irm.server.pooling.DataObjectPoolingService.access$000(DataObjectPoolingService.java:66)
at com.sas.solutions.risk.irm.server.pooling.DataObjectPoolingService$1.update(DataObjectPoolingService.java:341)
at java.util.Observable.notifyObservers(Observable.java:159)
at java.util.Observable.notifyObservers(Observable.java:115)
[...]
If the partitioned libraries are set as temporary libraries, the temporary data feature does not work properly for partitioned data, and the temporary partitioned data is not removed from the pool. In this scenario, large amounts of data might persist in the system.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Infrastructure for Risk Management | Microsoft® Windows® for x64 | 3.4 | 3.5 | 9.4 TS1M5 | 9.4 TS1M5 |
| Linux for x64 | 3.4 | 3.5 | 9.4 TS1M5 | 9.4 TS1M5 | ||